Release 10.1A: OpenEdge Development:
Messaging and ESB

Connection options

The OpenEdge Adapter for SonicMQ supports most of the same connection options as does the OpenEdge AppServer. You specify the desired options as the value of the adapterConnection parameter. Table 4–1 lists and explains the valid formats for expressing these options.

Table 4–1: OpenEdge Adapter for SonicMQ connection options

Connection option	Description
-H [ host_name | IP-address ]	Specifies the network address of a machine hosting a NameServer; or, if you use the -DirectConnect option, the address of a machine hosting a OpenEdge Adapter for SonicMQ. You can use either the TCP/IP host name or the IP address of the machine. (Defaults to localhost.)
-S [ port-number | service-name ]	Specifies the UDP port number for a NameServer; or, if you use the -DirectConnect option, the TCP/IP port number for a OpenEdge Adapter for SonicMQ. You can use either an explicit port number or a name associated with a port number in the TCP/IP services file. (Defaults to 5162 for a NameServer connection, or 3620 for a direct connection to a OpenEdge Adapter for SonicMQ.)
-DirectConnect	If included, causes the -H and -S parameters to be interpreted as the network address and TCP/IP port number of a specific OpenEdge Adapter for SonicMQ. If the -DirectConnect switch is omitted, the -H and -S parameters are interpreted as the network address and UDP port number of a NameServer.
-ssl	If included, specifies a secure connection to an SSL-enabled OpenEdge Adapter for SonicMQ. For more information, see OpenEdge Getting Started: Core Business Services .
-URL Web-or-AppServer-path	An HTTP- or HTTPS-based URL to an AppServer Internet Adapter (AIA), or an AppServer-based URL to a OpenEdge Adapter for SonicMQ to which you connect either directly or through a NameServer. This URL is identical in format to the URL used to connect Open Clients to an AppServer. The use of the -URL option precludes the use of the -H, -S, -DirectConnect, and -ssl options. The -URL parameter contains the necessary host and port information; it provides equivalent support for direct connections and secure SSL connections via AppServerDC, AppServerDCS, AppServerS, and HTTPS. For more information on the -URL connection option, see OpenEdge Application Server: Developing AppServer Applications . Note: The service name of the OpenEdge Adapter for SonicMQ is a required part of the -URL parameter. Therefore, if the application subsequently calls setAdapterService procedure, the call is ignored.
-nohostverify	If included, turns off host verification for a secure (SSL) connection. In the case of an SSL connection, unless this switch is included, the client compares the host name (specified in the -H parameter or the -URL parameter) with the Common Name specified in the server certificate, and raises an error if they do not match. With -nohostverify in effect, the client never raises the error. This option works only in the context of a secure connection; that is, in combination with the -ssl switch or with an HTTPS, AppServerS, or AppServerDCS parameter to the -URL switch. For more information, see OpenEdge Getting Started: Core Business Services .
-nosessionreuse	If included, prevents the application from reusing the session ID when reconnecting to the same SSL-enabled OpenEdge Adapter for SonicMQ. This option works only in the context of a secure (SSL) connection; that is, in combination with the -ssl switch or with an HTTPS, AppServerS, or AppServerDCS parameter to the -URL switch. For more information, see OpenEdge Getting Started: Core Business Services .
-pf pathname	Specifies a text file containing any of the AppServer connection parameters described in this table. Any other OpenEdge startup parameters in the file are ignored.
-SMQConnect	Creates a direct connection to the SonicMQ Broker using the jmssession.p Session object.

Table 4–2 shows several examples of valid adapterConnection parameters.

Table 4–2: Connection parameter examples

Connection parameter	Description
“”	By default, connection to the NameServer running on UDP port 5162 on localhost.
“-H host1 -S 5163”	Connection to the NameServer running on UDP port 5163 on the machine host1.
“-H fortress -S 3621 -DirectConnect -ssl -nohostverify	Secure connection directly to the SSL-enabled OpenEdge Adapter for SonicMQ running on TCP/IP port 3621 on the machine fortress, with host verification disabled.
“-URL http://host1:3099/external/aia1? adapter.progress.jms”	Connection by a WebClient via HTTP protocol to an AIA running on the machine host1.
“-URL AppServerDCS://fortress:3621/ -nosessionreuse”	Secure connection via AppServer protocol directly to an SSL-enabled OpenEdge Adapter for SonicMQ, with session reuse disabled.
RUN jms/jmssession.p PERSISTENT SET sessionH ("-SMQConnect").	Connects directly to the SonicMQ Broker allowing better connection and session management.

See the following manuals for more information:

OpenEdge Application Server: Developing AppServer Applications for details on URL-based connections. Although the discussion is in the context of AppServer connections, the same syntax rules apply to all OpenEdge Adapter for SonicMQ connections.
OpenEdge Application Server: Administration (and online help for the Progress Explorer tool) for instructions on enabling the OpenEdge Adapter for SonicMQ for SSL connections.
OpenEdge Getting Started: Core Business Services for a comprehensive discussion of SSL connections, management of keys and certificates, and other security considerations in OpenEdge.